						Rest Documentation for FLEXCUBE
						-------------------------------
1 Introduction:
----------------
This document contains instruction on how the template files can be referred to build GET and POST Requests.
Request and Response Templates for all the services have been placed in the templates folder.

2 Headers for all services in the Request to be posted:
-------------------------------------------------------
Below headers are to be populated for any request posted by the user to the service:
	a. SOURCE 	: Source Code of External System (Mandatory)
	b. USERID 	: FLEXCUBE User ID	(Mandatory)
	c. BRANCH 	: Transaction Branch Code (Mandatory)
	d. ENTITY 	: Entity ID (Not Mandatory)
	e. PASSWORD : Encrypted Oracle FLEXCUBE UBS login password using MSGID. (Not Mandatory)
	f. MSGID 	: Key used for encryption of password. (Not Mandatory)

3 Building Request using templates:
-----------------------------------
Template files contain information on the structure of Request URLs, Request Structures and Response Structures.
Referring to the template user can build the request for a given service.

3.1 Building GET Request from the template:
-------------------------------------------
"GET Method" in the template specifies the GET method URL for invoking the service. If set to "Not Applicable", GET operation is not enabled for this service.

Steps to derive the GET request URL:
<URL> indicates http protocol, Server ip and Server Port combination.
ex: http://10.10.10.10:1010
This has to be replaced in the template mentioned in the file.

3.2 Building POST Request from the template:
--------------------------------------------
"POST Methods" in the template specifies the POST method URL for invoking the service. If set to "Not Applicable", POST operation is not enabled for this service.

Steps to derive the POST request URL:
<URL> indicates http protocol, Server ip and Server Port combination.
ex: http://10.10.10.10:1010
This has to be replaced in the template mentioned in the file.

Steps to build the payload:
"BODY" specifies the template of the request which is to be posted for a POST request.
Value mentioned between "<>" has been set with the description specific to the field. User has to replace the complete content including "<>" with the data to be posted for the field.